Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce BookmarkManager #1285

Merged
merged 1 commit into from
Aug 16, 2022
Merged

Conversation

injectives
Copy link
Contributor

@injectives injectives commented Aug 8, 2022

Bookmark manager is a new opt-in feature that is enabled via driver Config.

It is responsible for providing an up-to-date set of bookmarks to driver on session creation and database data access.

Driver provides a default implementation via BookmarkManagers.defaultManager. The default implementation keeps track of a single local driver instance bookmarks only. However, it supports 2 extension points:
- updateListener - a listener for new bookmarks
- bookmarkSupplier - a supplier of additional bookmarks

It is possible to turn off bookmark manager on session level using SessionConfig even when it is enabled on the driver level.

Please note that this feature might have an impact on setups that do not manage the driver directly since there is a chance of getting a driver with bookmarks manager enabled.

Javadoc includes more general details.

@injectives injectives marked this pull request as draft August 8, 2022 11:01
@injectives injectives force-pushed the feature/bookmarkmanager branch 15 times, most recently from 96c9f27 to bfb1a37 Compare August 8, 2022 21:54
@injectives injectives changed the title bookmarkmanager Introduce BookmarkManager Aug 8, 2022
@injectives injectives force-pushed the feature/bookmarkmanager branch 13 times, most recently from 32c12cd to 6526902 Compare August 15, 2022 12:19
@injectives injectives requested a review from bigmontz August 15, 2022 12:19
@injectives injectives marked this pull request as ready for review August 15, 2022 12:19
@injectives injectives force-pushed the feature/bookmarkmanager branch 2 times, most recently from 249adb7 to 816ab27 Compare August 15, 2022 13:42
Bookmark manager is a new opt-in feature that is enabled via driver `Config`.

It is responsible for providing an up-to-date set of bookmarks to driver on session creation and database data access.

Driver provides a default implementation via `BookmarkManagers.defaultManager`. The default implementation keeps track of a single local driver instance bookmarks only. However, it supports 2 extension points:
- `updateListener` - a listener for new bookmarks
- `bookmarkSupplier` - a supplier of additional bookmarks

It is possible to turn off bookmark manager on session level using `SessionConfig` even when it is enabled on the driver level.

Please note that this feature might have an impact on setups that do not manage the driver directly since there is a chance of getting a driver with bookmarks manager enabled.

Javadoc includes more general details.
@injectives injectives force-pushed the feature/bookmarkmanager branch from 816ab27 to 2045d6c Compare August 15, 2022 14:43
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔖 🕴🏼

Please, you may have to do few tweaks in the backend for implementing the bookmark manager extension functions.

neo4j-drivers/testkit#506

@injectives injectives merged commit d63e21f into neo4j:5.0 Aug 16, 2022
@injectives injectives deleted the feature/bookmarkmanager branch August 16, 2022 08:38
@injectives
Copy link
Contributor Author

🔖 🕴🏼

Please, you may have to do few tweaks in the backend for implementing the bookmark manager extension functions.

neo4j-drivers/testkit#506

Thanks you. Sure, it will be updated separately.

@injectives
Copy link
Contributor Author

Further surface update: #1290

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants